Systems and methods for processing shape data based on serialization formatting

ABSTRACT

Systems, methods, and non-transitory computer-readable media can acquire shape data representative of one or more polygons. At least one serialization format can be produced based on the shape data. The at least one serialization format can be packaged into a proprietary package that is representative of the one or more polygons. At least a portion of the proprietary package can be utilized for one or more applications.

FIELD OF THE INVENTION

The present technology relates to the field of data processing. More particularly, the present technology relates to techniques for processing shape data based on serialization formatting.

BACKGROUND

Today, people often utilize computing devices (or systems) for a wide variety of purposes. Users can use their computing devices to, for example, interact with one another, access content, share content, and create content. In some cases, users can indicate their locations (e.g., addresses, hometowns, places of residency) via the computing devices. Moreover, in some instances, users such as organizations can utilize computing devices to produce locational, geographical, or shape data.

In one example, different users can create or generate differing locational, geographical, or shape data. Accordingly, there can be various instances and/or types of locational, geographical, or shape data. Conventional approaches specifically arising in the realm of computer technology can, in some cases, be inefficient, ineffective, or unreliable when attempting to utilize or process such various instances and/or types of locational, geographical, or shape data. As such, conventional approaches can create challenges for or reduce the overall experience associated with utilizing, accessing, or processing locational, geographical, or shape data.

SUMMARY

Various embodiments of the present disclosure can include systems, methods, and non-transitory computer readable media configured to acquire shape data representative of one or more polygons. At least one serialization format can be produced based on the shape data. The at least one serialization format can be packaged into a proprietary package that is representative of the one or more polygons. At least a portion of the proprietary package can be utilized for one or more applications.

In an embodiment, the shape data representative of the one or more polygons can be analyzed. At least one error associated with the shape data can be identified based on analyzing the shape data. The at least one error can be corrected prior to producing the at least one serialization format.

In an embodiment, the shape data representative of the one or more polygons can be associated with at least one of an Environmental Systems Research Institute (ESRI) format, a Network Common Data Form (NetCDF) format, a drawing (DWG) format, a Computer-Aided Design (CAD) format, a Well-Known Text (WKT) format, or a GeoJSON format.

In an embodiment, the at least one serialization format can be associated with at least one of an R serialization format, a data warehouse-compatible format, or a fortified format.

In an embodiment, the proprietary package can enable shape data acquired from different data sources to be standardized.

In an embodiment, the one or more applications can be associated with at least one of an entity framework, a geo-based application programming interface (API), or a real-time process.

In an embodiment, the one or more applications can be associated with the entity framework. The one or more applications can cause at least the portion of the proprietary package to be imported into a distributed data store that provides access to a social graph associated with a social networking system.

In an embodiment, the one or more applications can be associated with the real-time process. The one or more applications can cause at least the portion of the proprietary package to be utilized for real-time querying.

In an embodiment, the one or more applications can be associated with the geo-based application programming interface (API). The one or more applications can cause at least the portion of the proprietary package to be utilized for at least one of: 1) mapping a set of tiles associated with a social networking system to a set of polygons or 2) providing a prediction of a location for a user of the social networking system.

In an embodiment, mapping the set of tiles associated with the social networking system to the set of polygons can include: 1) mapping a first subset of tiles to a first subset of polygons and 2) mapping a second subset of tiles to a second subset of polygons. Mapping the first subset of tiles to the first subset of polygons can be performed via a first computing system. Mapping the second subset of tiles to the second subset of polygons can be performed via a second computing system.

It should be appreciated that many other features, applications, embodiments, and/or variations of the disclosed technology will be apparent from the accompanying drawings and from the following detailed description. Additional and/or alternative implementations of the structures, systems, non-transitory computer readable media, and methods described herein can be employed without departing from the principles of the disclosed technology.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system including an example shape data processing module configured to facilitate processing shape data based on serialization formatting, according to an embodiment of the present disclosure.

FIG. 2A illustrates an example serialization module configured to facilitate processing shape data based on serialization formatting, according to an embodiment of the present disclosure.

FIG. 2B illustrates an example application module configured to facilitate processing shape data based on serialization formatting, according to an embodiment of the present disclosure.

FIG. 3 illustrates an example scenario associated with processing shape data based on serialization formatting, according to an embodiment of the present disclosure.

FIG. 4 illustrates an example method associated with processing shape data based on serialization formatting, according to an embodiment of the present disclosure.

FIG. 5 illustrates an example method associated with processing shape data based on serialization formatting, according to an embodiment of the present disclosure.

FIG. 6 illustrates a network diagram of an example system including an example social networking system that can be utilized in various scenarios, according to an embodiment of the present disclosure.

FIG. 7 illustrates an example of a computer system or computing device that can be utilized in various scenarios, according to an embodiment of the present disclosure.

The figures depict various embodiments of the disclosed technology for purposes of illustration only, wherein the figures use like reference numerals to identify like elements. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated in the figures can be employed without departing from the principles of the disclosed technology described herein. It should be understood that all examples herein are provided for illustrative purposes and that there can be many variations or other possibilities associated with the disclosed technology.

DETAILED DESCRIPTION Processing Shape Data Based on Serialization Formatting

People use computing systems (or devices) for various purposes. Users can utilize their computing systems to establish connections, engage in communications, interact with one another, and/or interact with various types of content. In some cases, a user can indicate his or her location(s) (e.g., address, hometown, place of residency) via a computing device. For instance, users of a social networking system can check in at, log in at, or otherwise input various locations, which can be recognized by the social networking system as location entities (e.g., places). Moreover, in some cases, users such as organizations can utilize computing devices to produce locational, geographical, or shape data. For example, organizations can utilize certain software on computing devices to create and provide shape data corresponding to one or more polygons that represent one or more real-world geographic areas (e.g., regions).

In many instances, conventional approaches specifically arising in the realm of computer technology can attempt to utilize, develop, access, or otherwise process such locational, geographical, or shape data. Under conventional approaches, different users can, for example, create or generate differing locational, geographical, or shape data, resulting in various instances and/or types of locational, geographical, or shape data. As such, conventional approaches can be directed away from standardization and/or uniformity with regard to locational, geographical, or shape data. It follows that conventional approaches specifically arising in the realm of computer technology can, in many cases, be inefficient, ineffective, or unreliable when attempting to utilize, develop, access, or otherwise process locational, geographical, or shape data.

Due to these or other concerns, conventional approaches specifically arising in the realm of computer technology can be disadvantageous or problematic. Therefore, an improved approach rooted in computer technology that overcomes the foregoing and other disadvantages associated with conventional approaches can be beneficial. Based on computer technology, the disclosed technology can process shape data based on serialization formatting. Thus, the disclosed technology can, in some cases, enable shape data acquired from different data sources to be substantially standardized or made substantially uniform. Various embodiments of the present disclosure can acquire shape data representative of one or more polygons. At least one serialization format can be produced based on the shape data. The at least one serialization format can be packaged into a proprietary package that is representative of the one or more polygons. At least a portion of the proprietary package can be utilized for one or more applications. In some embodiments, the disclosed technology advantageously can be used in conjunction with a data warehouse system (e.g., a data warehouse system for Hadoop) that facilitates optimal data summarization, ad-hoc queries, analysis of large datasets, and big data parallel processing. It is contemplated that there can be many variations and/or other possibilities associated with the disclosed technology.

FIG. 1 illustrates an example system 100 including an example shape data processing module 102 configured to facilitate processing shape data based on serialization formatting, according to an embodiment of the present disclosure. As shown in the example of FIG. 1, the shape data processing module 102 can include a shape data module 104, a serialization module 106, a package module 108, and an application module 110. In some instances, the example system 100 can include at least one data store 120. The components (e.g., modules, elements, etc.) shown in this figure and all figures herein are exemplary only, and other implementations may include additional, fewer, integrated, or different components. Some components may not be shown so as not to obscure relevant details.

In some embodiments, the shape data processing module 102 can be implemented, in part or in whole, as software, hardware, or any combination thereof. In general, a module as discussed herein can be associated with software, hardware, or any combination thereof. In some implementations, one or more functions, tasks, and/or operations of modules can be carried out or performed by software routines, software processes, hardware, and/or any combination thereof. In some cases, the shape data processing module 102 can be implemented, in part or in whole, as software running on one or more computing devices or systems, such as on a user or client computing device. For example, the shape data processing module 102 or at least a portion thereof can be implemented as or within an application (e.g., app), a program, an applet, or an operating system, etc., running on a user computing device or a client computing system, such as the user device 610 of FIG. 6. In another example, the shape data processing module 102 or at least a portion thereof can be implemented using one or more computing devices or systems which can include one or more servers, such as network servers or cloud servers. In some instances, the shape data processing module 102 can, in part or in whole, be implemented within or configured to operate in conjunction with a social networking system (or service), such as the social networking system 630 of FIG. 6. It should be appreciated that there can be many variations or other possibilities.

The shape data module 104 can be configured to facilitate acquiring shape data representative of one or more polygons. The shape data module 104 can be configured to receive, retrieve, or otherwise acquire the shape data representative of (or corresponding to) the one or more polygons, which can be intended to be associated with one or more real-world geographical regions or areas.

In some embodiments, the shape data module 104 can acquire one or more collections of shape data from one or more data sources (e.g., third-party shape data providers). In some cases, such data sources can be different. Moreover, the collections of shape data acquired by the shape data module 104 can also be different. For instance, multiple collections of shape data can correspond to or represent different sets of polygons. In another instance, multiple collections of shape data can have different formats, even if the multiple collections represent or correspond to the same set of polygons. In some cases, the shape data representative of the one or more polygons can be associated with at least one of an Environmental Systems Research Institute (ESRI) format, a Network Common Data Form (NetCDF) format, a drawing (DWG) format, a Computer-Aided Design (CAD) format, a Well-Known Text (WKT) format, or a GeoJSON format, etc.

Furthermore, in some cases, acquired shape data can include errors or inconsistencies (e.g., non-noded intersections, unclosed polygons, etc.). The shape data module 104 can be configured to facilitate reading, parsing, or otherwise analyzing the shape data. Based on analyzing the shape data, the shape data module 104 can attempt to identify at least one error associated with or included in the shape data. In some implementations, the shape data module 104 can attempt to correct or fix the at least one error. For example, if the at least one error corresponds to an unclosed polygon, then the shape data module 104 can attempt to close the polygon (e.g., connect vertices of the polygon). It is contemplated that all examples herein are provided for illustrative purposes and that many variations associated with the disclosed technology are possible. For instance, in some cases, the shape data module 104 can facilitate checking licensing information associated with the acquired shape data.

In addition, the serialization module 106 can be configured to facilitate producing at least one serialization format based on the acquired shape data. This can facilitate enabling the shape data to be (substantially) standardized or made (substantially) uniform (e.g., standardized within an allowable deviation, uniform within an allowable deviation, etc.). More details regarding the serialization module 106 will be provided below with reference to FIG. 2A.

Moreover, the package module 108 can be configured to facilitate packaging the at least one serialization format into a proprietary package that is representative of the one or more polygons. In some embodiments, the proprietary package assembled, packaged, or otherwise generated by the package module 108 based on the at least one serialization format can correspond to a proprietary data structure utilized by a social networking system. The package module 108 can also, in some cases, permit different versions of each proprietary package.

In some instances, the proprietary package resulting from packaging the at least one serialization format can enable shape data acquired from different data sources to be standardized, such as in a proprietary manner. For example, different collections of shape data can be serialized and packaged proprietarily in accordance with the disclosed technology. In this example, the resulting proprietary packages derived from the different collections of shape data can be associated with the same proprietary standard/format provided by the disclosed technology.

Further, the application module 110 can be configured to facilitate utilizing at least a portion of the proprietary package for one or more applications. The application module 110 can, for instance, enable at least the portion of the proprietary package to be utilized by one or more applications, programs, or other processes. The application module 110 will be discussed in more detail below with reference to FIG. 2B.

Additionally, in some embodiments, the shape data processing module 102 can be configured to communicate and/or operate with the at least one data store 120, as shown in the example system 100. The at least one data store 120 can be configured to store and maintain various types of data. In some implementations, the at least one data store 120 can store information associated with the social networking system (e.g., the social networking system 630 of FIG. 6). The information associated with the social networking system can include data about users, social connections, social interactions, locations, geo-fenced areas, maps, places, events, pages, groups, posts, communications, content, feeds, account settings, privacy settings, a social graph, and various other types of data. In some implementations, the at least one data store 120 can store information associated with users, such as user identifiers, user information, profile information, user locations, user specified settings, content produced or posted by users, and various other types of user data. In some embodiments, the at least one data store 120 can store information that is utilized by the shape data processing module 102. Again, it is contemplated that there can be many variations or other possibilities associated with the disclosed technology.

FIG. 2A illustrates an example serialization module 202 configured to facilitate processing shape data based on serialization formatting, according to an embodiment of the present disclosure. In some embodiments, the serialization module 106 of FIG. 1 can be implemented as the example serialization module 202. As shown in FIG. 2A, the serialization module 202 can include an R serialization format module 204, a data warehouse-compatible format module 206, and a fortified format module 208.

As discussed previously, the serialization module 202 can be configured to facilitate producing at least one serialization format based on acquired shape data, which can be representative of one or more polygons. In some cases, the at least one serialization format can be associated with at least one of an R serialization format, a data warehouse-compatible format, or a fortified format. The R serialization format can, for instance, correspond to a “.RDS” file format. The R serialization format can be associated with a representation of a SpatialPolygonDataFrame, which can correspond to a standardized data structure in R that is configured for geographic information systems. The data warehouse-compatible format can, for example, correspond to a proprietary serialization format utilized by a social networking system. The data warehouse-compatible format can include, for each polygon, an identifier, a name, and polygonal coordinates (e.g., in Well-Known Text). Further, the fortified format can, for instance, correspond to a serialization format that specifies an identifier and a set of vertices (e.g., X coordinates, Y Coordinates, etc.) for each of the polygons. The fortified format can include a identifier column, an X coordinate vertex column, and a Y coordinate vertex column, etc. In some embodiments, the fortified format is based on ggplot2, a data visualization package for the statistical programming language R, and is a way to represent a polygon in a tabular format. In some instances, one or more of the serialization formats can also include metadata, such as for storing data source annotations or other information.

In some embodiments, the serialization module 202 can utilize one or more scripts to produce the at least one serialization format based on the acquired shape data. The serialization module 202 can utilize the R serialization format module 204 to facilitate producing the at least one serialization format to include the R serialization format. The serialization module 202 can utilize the data warehouse-compatible format module 206 to facilitate producing the at least one serialization format to include the data warehouse-compatible format. Moreover, the serialization module 202 can utilize the fortified format module 208 to facilitate producing the at least one serialization format to include the fortified format. Each of the R serialization format, the data warehouse-compatible format, and the fortified format can be useful or more suitably configured for utilization in one or more respective tasks or applications. In one example, the R serialization format can be utilized (more efficiently) for various topological manipulation purposes or mapping purposes (e.g., mapping tiles to polygons or vice versa). In another example, the data warehouse-compatible format can (more efficiently) enable certain information about a particular polygon to be received, retrieved, or otherwise acquired, such as for querying purposes or rendering purposes. In a further example, the fortified format can be utilized (more efficiently) for visualization purposes or plotting purposes, such as when graph generation requires a table(s) in which rows represent polygonal vertices. Many variations are possible.

Furthermore, in some implementations, the R serialization format module 204, the data warehouse-compatible format module 206, and/or the fortified format module 208 can operate in conjunction and/or can be compatible with one another. Accordingly, the at least one serialization format can include any combination of the R serialization format, the data warehouse-compatible format, and/or the fortified format, etc. For example, in some instances, the at least one serialization format can include each of the R serialization format, the data warehouse-compatible format, and the fortified format. It should be understood that all examples herein are provided for illustrative purposes and that there can be many variations or other possibilities associated with the disclosed technology.

FIG. 2B illustrates an example application module 222 configured to facilitate processing shape data based on serialization formatting, according to an embodiment of the present disclosure. In some embodiments, the application module 110 of FIG. 1 can be implemented as the example application module 222. As shown in FIG. 2B, the example application module 222 can include an entity framework module 224, a geo-based application programming interface (API) module 226, and a real-time module 228.

The application module 222 can be configured to facilitate utilizing at least a portion of a proprietary package for one or more applications. In some embodiments, the one or more applications can be associated with at least one of an entity framework, a geo-based application programming interface (API), or a real-time process. In one example, an application can be associated with an entity framework. The application module 222 can utilize the entity framework module 224 to facilitate performing one or more tasks associated with the application. In this example, the entity framework module 224 can enable the application to cause at least a portion of the proprietary package to be imported into a distributed data store that provides access to a social graph associated with a social networking system. The social graph associated with the social networking system can provide one or more representations of one or more entities (e.g., users, places, pages, businesses, etc.).

In another example, an application can be associated with a geo-based API. The application module 222 can utilize the geo-based API module 226 to facilitate performing one or more tasks associated with the application. In this example, the geo-based API module 226 can enable the application to cause at least a portion of the proprietary package to be utilized for mapping a set of tiles associated with a social networking system to a set of polygons and/or for providing a prediction of a location (e.g., current location, inputted location, residence, hometown, etc.) for a user of the social networking system. In some instances, mapping the set of tiles associated with the social networking system to the set of polygons can include mapping a first subset of tiles to a first subset of polygons as well as mapping a second subset of tiles to a second subset of polygons. The disclosed technology can enable mapping the first subset of tiles to the first subset of polygons to be performed via a first computing system, and can enable mapping the second subset of tiles to the second subset of polygons to be performed via a second computing system.

In further example, an application can be associated with a real-time process. The application module 222 can utilize the real-time module 228 to facilitate performing one or more tasks associated with the application. In this example, the real-time module 228 can enable the application to cause at least a portion of the proprietary package to be utilized for real-time querying, such as for real-time point-in-polygon mapping. As discussed, it should be appreciated that all examples herein are provided for illustrative purposes and that many variations associated with the disclosed technology are possible.

FIG. 3 illustrates an example scenario 300 associated with processing shape data based on serialization formatting, according to an embodiment of the present disclosure. As shown in the example scenario 300, there can be a plurality of data sources, such as Data Source A 302, Data Source B 304, and Data Source C 306, etc. In some cases, at least some of the data sources can include third-party providers of shape data. In this example scenario 300, Data Source A 302 can provide a first set of shape data (e.g., Data A 312), Data Source B 304 can provide a second set of shape data (e.g., Data B 314), and Data Source C 306 can provide a third set of shape data (e.g., Data C 316). The disclosed technology can be configured to receive, retrieve, or otherwise acquire such shape data provided via the data sources.

Moreover, the disclosed technology can perform serialization 320 with respect to each of the first set of shape data (e.g., Data A 312), the second set of shape data (e.g., Data B 314), and the third set of shape data (e.g., Data C 316). As a result, each of the first set of shape data (e.g., Data A 312), the second set of shape data (e.g., Data B 314), and the third set of shape data (e.g., Data C 316) can be represented respectively via at least one serialization format. Although not explicitly illustrated in FIG. 3, there can be a first serialization format(s) for the first set of shape data (e.g., Data A 312), a second serialization format(s) for the second set of shape data (e.g., Data B 314), and a third serialization format(s) for the third set of shape data (e.g., Data C 316). Additionally, the disclosed technology can package 330 each of the first serialization format(s), the second serialization format(s), and the third serialization format(s) to respectively produce a first proprietary package, a second proprietary package, and a third proprietary package. (These proprietary packages are not explicitly illustrated in FIG. 3.)

Furthermore, each of the proprietary packages (or one or more portions thereof) can be utilized for one or more applications. As shown in the example scenario 300, the one or more applications can be associated with at least one of an entity framework 342, a geo-based application programming interface (API) 344, and/or a real-time process 346, etc. Again, it should be understood that there can be many variations or other possibilities associated with the disclosed technology.

FIG. 4 illustrates an example method 400 associated with processing shape data based on serialization formatting, according to an embodiment of the present disclosure. It should be appreciated that there can be additional, fewer, or alternative steps performed in similar or alternative orders, or in parallel, within the scope of the various embodiments unless otherwise stated.

At block 402, the example method 400 can acquire shape data representative of one or more polygons. At block 404, the example method 400 can produce at least one serialization format based on the shape data. At block 406, the example method 400 can package the at least one serialization format into a proprietary package that is representative of the one or more polygons. At block 408, the example method 400 can utilize at least a portion of the proprietary package for one or more applications.

FIG. 5 illustrates an example method 500 associated with processing shape data based on serialization formatting, according to an embodiment of the present disclosure. As discussed, it should be understood that there can be additional, fewer, or alternative steps performed in similar or alternative orders, or in parallel, within the scope of the various embodiments unless otherwise stated.

At block 502, the example method 500 can analyze the shape data representative of the one or more polygons. At block 504, the example method 500 can identify, based on analyzing the shape data, at least one error associated with the shape data. At block 506, the example method 500 can correct, prior to producing the at least one serialization format, the at least one error.

It is contemplated that there can be many other uses, applications, features, possibilities, and/or variations associated with various embodiments of the present disclosure. For example, users can, in some cases, choose whether or not to opt-in to utilize the disclosed technology. The disclosed technology can, for instance, also ensure that various privacy settings, preferences, and configurations are maintained and can prevent private information from being divulged. In another example, various embodiments of the present disclosure can learn, improve, and/or be refined over time.

Social Networking System—Example Implementation

FIG. 6 illustrates a network diagram of an example system 600 that can be utilized in various scenarios, in accordance with an embodiment of the present disclosure. The system 600 includes one or more user devices 610, one or more external systems 620, a social networking system (or service) 630, and a network 650. In an embodiment, the social networking service, provider, and/or system discussed in connection with the embodiments described above may be implemented as the social networking system 630. For purposes of illustration, the embodiment of the system 600, shown by FIG. 6, includes a single external system 620 and a single user device 610. However, in other embodiments, the system 600 may include more user devices 610 and/or more external systems 620. In certain embodiments, the social networking system 630 is operated by a social network provider, whereas the external systems 620 are separate from the social networking system 630 in that they may be operated by different entities. In various embodiments, however, the social networking system 630 and the external systems 620 operate in conjunction to provide social networking services to users (or members) of the social networking system 630. In this sense, the social networking system 630 provides a platform or backbone, which other systems, such as external systems 620, may use to provide social networking services and functionalities to users across the Internet. In some embodiments, the social networking system 630 can include or correspond to a social media system (or service).

The user device 610 comprises one or more computing devices (or systems) that can receive input from a user and transmit and receive data via the network 650. In one embodiment, the user device 610 is a conventional computer system executing, for example, a Microsoft Windows compatible operating system (OS), Apple OS X, and/or a Linux distribution. In another embodiment, the user device 610 can be a computing device or a device having computer functionality, such as a smart-phone, a tablet, a personal digital assistant (PDA), a mobile telephone, a laptop computer, a wearable device (e.g., a pair of glasses, a watch, a bracelet, etc.), a camera, an appliance, etc. The user device 610 is configured to communicate via the network 650. The user device 610 can execute an application, for example, a browser application that allows a user of the user device 610 to interact with the social networking system 630. In another embodiment, the user device 610 interacts with the social networking system 630 through an application programming interface (API) provided by the native operating system of the user device 610, such as iOS and ANDROID. The user device 610 is configured to communicate with the external system 620 and the social networking system 630 via the network 650, which may comprise any combination of local area and/or wide area networks, using wired and/or wireless communication systems.

In one embodiment, the network 650 uses standard communications technologies and protocols. Thus, the network 650 can include links using technologies such as Ethernet, 802.11 (e.g., Wi-Fi), worldwide interoperability for microwave access (WiMAX), 3G, 4G, CDMA, GSM, LTE, digital subscriber line (DSL), etc. Similarly, the networking protocols used on the network 650 can include multiprotocol label switching (MPLS), transmission control protocol/Internet protocol (TCP/IP), User Datagram Protocol (UDP), hypertext transport protocol (HTTP), simple mail transfer protocol (SMTP), file transfer protocol (FTP), and the like. The data exchanged over the network 650 can be represented using technologies and/or formats including hypertext markup language (HTML) and extensible markup language (XML). In addition, all or some links can be encrypted using conventional encryption technologies such as secure sockets layer (SSL), transport layer security (TLS), and Internet Protocol security (IPsec).

In one embodiment, the user device 610 may display content from the external system 620 and/or from the social networking system 630 by processing a markup language document 614 received from the external system 620 and from the social networking system 630 using a browser application 612. The markup language document 614 identifies content and one or more instructions describing formatting or presentation of the content. By executing the instructions included in the markup language document 614, the browser application 612 displays the identified content using the format or presentation described by the markup language document 614. For example, the markup language document 614 includes instructions for generating and displaying a web page having multiple frames that include text and/or image data retrieved from the external system 620 and the social networking system 630. In various embodiments, the markup language document 614 comprises a data file including extensible markup language (XML) data, extensible hypertext markup language (XHTML) data, or other markup language data. Additionally, the markup language document 614 may include JavaScript Object Notation (JSON) data, JSON with padding (JSONP), and JavaScript data to facilitate data-interchange between the external system 620 and the user device 610. The browser application 612 on the user device 610 may use a JavaScript compiler to decode the markup language document 614.

The markup language document 614 may also include, or link to, applications or application frameworks such as FLASH™ or Unity™ applications, the Silverlight™ application framework, etc.

In one embodiment, the user device 610 also includes one or more cookies 616 including data indicating whether a user of the user device 610 is logged into the social networking system 630, which may enable modification of the data communicated from the social networking system 630 to the user device 610.

The external system 620 includes one or more web servers that include one or more web pages 622 a, 622 b, which are communicated to the user device 610 using the network 650. The external system 620 is separate from the social networking system 630. For example, the external system 620 is associated with a first domain, while the social networking system 630 is associated with a separate social networking domain. Web pages 622 a, 622 b, included in the external system 620, comprise markup language documents 614 identifying content and including instructions specifying formatting or presentation of the identified content.

The social networking system 630 includes one or more computing devices for a social network, including a plurality of users, and providing users of the social network with the ability to communicate and interact with other users of the social network. In some instances, the social network can be represented by a graph, i.e., a data structure including edges and nodes. Other data structures can also be used to represent the social network, including but not limited to databases, objects, classes, meta elements, files, or any other data structure. The social networking system 630 may be administered, managed, or controlled by an operator. The operator of the social networking system 630 may be a human being, an automated application, or a series of applications for managing content, regulating policies, and collecting usage metrics within the social networking system 630. Any type of operator may be used.

Users may join the social networking system 630 and then add connections to any number of other users of the social networking system 630 to whom they desire to be connected. As used herein, the term “friend” refers to any other user of the social networking system 630 to whom a user has formed a connection, association, or relationship via the social networking system 630. For example, in an embodiment, if users in the social networking system 630 are represented as nodes in the social graph, the term “friend” can refer to an edge formed between and directly connecting two user nodes.

Connections may be added explicitly by a user or may be automatically created by the social networking system 630 based on common characteristics of the users (e.g., users who are alumni of the same educational institution). For example, a first user specifically selects a particular other user to be a friend. Connections in the social networking system 630 are usually in both directions, but need not be, so the terms “user” and “friend” depend on the frame of reference. Connections between users of the social networking system 630 are usually bilateral (“two-way”), or “mutual,” but connections may also be unilateral, or “one-way.” For example, if Bob and Joe are both users of the social networking system 630 and connected to each other, Bob and Joe are each other's connections. If, on the other hand, Bob wishes to connect to Joe to view data communicated to the social networking system 630 by Joe, but Joe does not wish to form a mutual connection, a unilateral connection may be established. The connection between users may be a direct connection; however, some embodiments of the social networking system 630 allow the connection to be indirect via one or more levels of connections or degrees of separation.

In addition to establishing and maintaining connections between users and allowing interactions between users, the social networking system 630 provides users with the ability to take actions on various types of items supported by the social networking system 630. These items may include groups or networks (i.e., social networks of people, entities, and concepts) to which users of the social networking system 630 may belong, events or calendar entries in which a user might be interested, computer-based applications that a user may use via the social networking system 630, transactions that allow users to buy or sell items via services provided by or through the social networking system 630, and interactions with advertisements that a user may perform on or off the social networking system 630. These are just a few examples of the items upon which a user may act on the social networking system 630, and many others are possible. A user may interact with anything that is capable of being represented in the social networking system 630 or in the external system 620, separate from the social networking system 630, or coupled to the social networking system 630 via the network 650.

The social networking system 630 is also capable of linking a variety of entities. For example, the social networking system 630 enables users to interact with each other as well as external systems 620 or other entities through an API, a web service, or other communication channels. The social networking system 630 generates and maintains the “social graph” comprising a plurality of nodes interconnected by a plurality of edges. Each node in the social graph may represent an entity that can act on another node and/or that can be acted on by another node. The social graph may include various types of nodes. Examples of types of nodes include users, non-person entities, content items, web pages, groups, activities, messages, concepts, and any other things that can be represented by an object in the social networking system 630. An edge between two nodes in the social graph may represent a particular kind of connection, or association, between the two nodes, which may result from node relationships or from an action that was performed by one of the nodes on the other node. In some cases, the edges between nodes can be weighted. The weight of an edge can represent an attribute associated with the edge, such as a strength of the connection or association between nodes. Different types of edges can be provided with different weights. For example, an edge created when one user “likes” another user may be given one weight, while an edge created when a user befriends another user may be given a different weight.

As an example, when a first user identifies a second user as a friend, an edge in the social graph is generated connecting a node representing the first user and a second node representing the second user. As various nodes relate or interact with each other, the social networking system 630 modifies edges connecting the various nodes to reflect the relationships and interactions.

The social networking system 630 also includes user-generated content, which enhances a user's interactions with the social networking system 630. User-generated content may include anything a user can add, upload, send, or “post” to the social networking system 630. For example, a user communicates posts to the social networking system 630 from a user device 610. Posts may include data such as status updates or other textual data, location information, images such as photos, videos, links, music or other similar data and/or media. Content may also be added to the social networking system 630 by a third party. Content “items” are represented as objects in the social networking system 630. In this way, users of the social networking system 630 are encouraged to communicate with each other by posting text and content items of various types of media through various communication channels. Such communication increases the interaction of users with each other and increases the frequency with which users interact with the social networking system 630.

The social networking system 630 includes a web server 632, an API request server 634, a user profile store 636, a connection store 638, an action logger 640, an activity log 642, and an authorization server 644. In an embodiment of the invention, the social networking system 630 may include additional, fewer, or different components for various applications. Other components, such as network interfaces, security mechanisms, load balancers, failover servers, management and network operations consoles, and the like are not shown so as to not obscure the details of the system.

The user profile store 636 maintains information about user accounts, including biographic, demographic, and other types of descriptive information, such as work experience, educational history, hobbies or preferences, location, and the like that has been declared by users or inferred by the social networking system 630. This information is stored in the user profile store 636 such that each user is uniquely identified. The social networking system 630 also stores data describing one or more connections between different users in the connection store 638. The connection information may indicate users who have similar or common work experience, group memberships, hobbies, or educational history. Additionally, the social networking system 630 includes user-defined connections between different users, allowing users to specify their relationships with other users. For example, user-defined connections allow users to generate relationships with other users that parallel the users' real-life relationships, such as friends, co-workers, partners, and so forth. Users may select from predefined types of connections, or define their own connection types as needed. Connections with other nodes in the social networking system 630, such as non-person entities, buckets, cluster centers, images, interests, pages, external systems, concepts, and the like are also stored in the connection store 638.

The social networking system 630 maintains data about objects with which a user may interact. To maintain this data, the user profile store 636 and the connection store 638 store instances of the corresponding type of objects maintained by the social networking system 630. Each object type has information fields that are suitable for storing information appropriate to the type of object. For example, the user profile store 636 contains data structures with fields suitable for describing a user's account and information related to a user's account. When a new object of a particular type is created, the social networking system 630 initializes a new data structure of the corresponding type, assigns a unique object identifier to it, and begins to add data to the object as needed. This might occur, for example, when a user becomes a user of the social networking system 630, the social networking system 630 generates a new instance of a user profile in the user profile store 636, assigns a unique identifier to the user account, and begins to populate the fields of the user account with information provided by the user.

The connection store 638 includes data structures suitable for describing a user's connections to other users, connections to external systems 620 or connections to other entities. The connection store 638 may also associate a connection type with a user's connections, which may be used in conjunction with the user's privacy setting to regulate access to information about the user. In an embodiment of the invention, the user profile store 636 and the connection store 638 may be implemented as a federated database.

Data stored in the connection store 638, the user profile store 636, and the activity log 642 enables the social networking system 630 to generate the social graph that uses nodes to identify various objects and edges connecting nodes to identify relationships between different objects. For example, if a first user establishes a connection with a second user in the social networking system 630, user accounts of the first user and the second user from the user profile store 636 may act as nodes in the social graph. The connection between the first user and the second user stored by the connection store 638 is an edge between the nodes associated with the first user and the second user. Continuing this example, the second user may then send the first user a message within the social networking system 630. The action of sending the message, which may be stored, is another edge between the two nodes in the social graph representing the first user and the second user. Additionally, the message itself may be identified and included in the social graph as another node connected to the nodes representing the first user and the second user.

In another example, a first user may tag a second user in an image that is maintained by the social networking system 630 (or, alternatively, in an image maintained by another system outside of the social networking system 630). The image may itself be represented as a node in the social networking system 630. This tagging action may create edges between the first user and the second user as well as create an edge between each of the users and the image, which is also a node in the social graph. In yet another example, if a user confirms attending an event, the user and the event are nodes obtained from the user profile store 636, where the attendance of the event is an edge between the nodes that may be retrieved from the activity log 642. By generating and maintaining the social graph, the social networking system 630 includes data describing many different types of objects and the interactions and connections among those objects, providing a rich source of socially relevant information.

The web server 632 links the social networking system 630 to one or more user devices 610 and/or one or more external systems 620 via the network 650. The web server 632 serves web pages, as well as other web-related content, such as Java, JavaScript, Flash, XML, and so forth. The web server 632 may include a mail server or other messaging functionality for receiving and routing messages between the social networking system 630 and one or more user devices 610. The messages can be instant messages, queued messages (e.g., email), text and SMS messages, or any other suitable messaging format.

The API request server 634 allows one or more external systems 620 and user devices 610 to call access information from the social networking system 630 by calling one or more API functions. The API request server 634 may also allow external systems 620 to send information to the social networking system 630 by calling APIs. The external system 620, in one embodiment, sends an API request to the social networking system 630 via the network 650, and the API request server 634 receives the API request. The API request server 634 processes the request by calling an API associated with the API request to generate an appropriate response, which the API request server 634 communicates to the external system 620 via the network 650. For example, responsive to an API request, the API request server 634 collects data associated with a user, such as the user's connections that have logged into the external system 620, and communicates the collected data to the external system 620. In another embodiment, the user device 610 communicates with the social networking system 630 via APIs in the same manner as external systems 620.

The action logger 640 is capable of receiving communications from the web server 632 about user actions on and/or off the social networking system 630. The action logger 640 populates the activity log 642 with information about user actions, enabling the social networking system 630 to discover various actions taken by its users within the social networking system 630 and outside of the social networking system 630. Any action that a particular user takes with respect to another node on the social networking system 630 may be associated with each user's account, through information maintained in the activity log 642 or in a similar database or other data repository. Examples of actions taken by a user within the social networking system 630 that are identified and stored may include, for example, adding a connection to another user, sending a message to another user, reading a message from another user, viewing content associated with another user, attending an event posted by another user, posting an image, attempting to post an image, or other actions interacting with another user or another object. When a user takes an action within the social networking system 630, the action is recorded in the activity log 642. In one embodiment, the social networking system 630 maintains the activity log 642 as a database of entries. When an action is taken within the social networking system 630, an entry for the action is added to the activity log 642. The activity log 642 may be referred to as an action log.

Additionally, user actions may be associated with concepts and actions that occur within an entity outside of the social networking system 630, such as an external system 620 that is separate from the social networking system 630. For example, the action logger 640 may receive data describing a user's interaction with an external system 620 from the web server 632. In this example, the external system 620 reports a user's interaction according to structured actions and objects in the social graph.

Other examples of actions where a user interacts with an external system 620 include a user expressing an interest in an external system 620 or another entity, a user posting a comment to the social networking system 630 that discusses an external system 620 or a web page 622 a within the external system 620, a user posting to the social networking system 630 a Uniform Resource Locator (URL) or other identifier associated with an external system 620, a user attending an event associated with an external system 620, or any other action by a user that is related to an external system 620. Thus, the activity log 642 may include actions describing interactions between a user of the social networking system 630 and an external system 620 that is separate from the social networking system 630.

The authorization server 644 enforces one or more privacy settings of the users of the social networking system 630. A privacy setting of a user determines how particular information associated with a user can be shared. The privacy setting comprises the specification of particular information associated with a user and the specification of the entity or entities with whom the information can be shared. Examples of entities with which information can be shared may include other users, applications, external systems 620, or any entity that can potentially access the information. The information that can be shared by a user comprises user account information, such as profile photos, phone numbers associated with the user, user's connections, actions taken by the user such as adding a connection, changing user profile information, and the like.

The privacy setting specification may be provided at different levels of granularity. For example, the privacy setting may identify specific information to be shared with other users; the privacy setting identifies a work phone number or a specific set of related information, such as, personal information including profile photo, home phone number, and status. Alternatively, the privacy setting may apply to all the information associated with the user. The specification of the set of entities that can access particular information can also be specified at various levels of granularity. Various sets of entities with which information can be shared may include, for example, all friends of the user, all friends of friends, all applications, or all external systems 620. One embodiment allows the specification of the set of entities to comprise an enumeration of entities. For example, the user may provide a list of external systems 620 that are allowed to access certain information. Another embodiment allows the specification to comprise a set of entities along with exceptions that are not allowed to access the information. For example, a user may allow all external systems 620 to access the user's work information, but specify a list of external systems 620 that are not allowed to access the work information. Certain embodiments call the list of exceptions that are not allowed to access certain information a “block list”. External systems 620 belonging to a block list specified by a user are blocked from accessing the information specified in the privacy setting. Various combinations of granularity of specification of information, and granularity of specification of entities, with which information is shared are possible. For example, all personal information may be shared with friends whereas all work information may be shared with friends of friends.

The authorization server 644 contains logic to determine if certain information associated with a user can be accessed by a user's friends, external systems 620, and/or other applications and entities. The external system 620 may need authorization from the authorization server 644 to access the user's more private and sensitive information, such as the user's work phone number. Based on the user's privacy settings, the authorization server 644 determines if another user, the external system 620, an application, or another entity is allowed to access information associated with the user, including information about actions taken by the user.

In some embodiments, the social networking system 630 can include an shape data processing module 646. The shape data processing module 646 can, for example, be implemented as the shape data processing module 102 of FIG. 1. As discussed previously, it should be appreciated that there can be many variations or other possibilities associated with the disclosed technology. For example, in some instances, the shape data processing module (or at least a portion thereof) can be included or implemented in the user device 610. Other features of the shape data processing module 646 are discussed herein in connection with the shape data processing module 102.

Hardware Implementation

The foregoing processes and features can be implemented by a wide variety of machine and computer system architectures and in a wide variety of network and computing environments. FIG. 7 illustrates an example of a computer system 700 that may be used to implement one or more of the embodiments described herein in accordance with an embodiment of the invention. The computer system 700 includes sets of instructions for causing the computer system 700 to perform the processes and features discussed herein. The computer system 700 may be connected (e.g., networked) to other machines. In a networked deployment, the computer system 700 may operate in the capacity of a server machine or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. In an embodiment of the invention, the computer system 700 may be the social networking system 630, the user device 610, and the external system 620, or a component thereof. In an embodiment of the invention, the computer system 700 may be one server among many that constitutes all or part of the social networking system 630.

The computer system 700 includes a processor 702, a cache 704, and one or more executable modules and drivers, stored on a computer-readable medium, directed to the processes and features described herein. Additionally, the computer system 700 includes a high performance input/output (I/O) bus 706 and a standard I/O bus 708. A host bridge 710 couples processor 702 to high performance I/O bus 706, whereas I/O bus bridge 712 couples the two buses 706 and 708 to each other. A system memory 714 and one or more network interfaces 716 couple to high performance I/O bus 706. The computer system 700 may further include video memory and a display device coupled to the video memory (not shown). Mass storage 718 and I/O ports 720 couple to the standard I/O bus 708. The computer system 700 may optionally include a keyboard and pointing device, a display device, or other input/output devices (not shown) coupled to the standard I/O bus 708. Collectively, these elements are intended to represent a broad category of computer hardware systems, including but not limited to computer systems based on the x86-compatible processors manufactured by Intel Corporation of Santa Clara, Calif., and the x86-compatible processors manufactured by Advanced Micro Devices (AMD), Inc., of Sunnyvale, Calif., as well as any other suitable processor.

An operating system manages and controls the operation of the computer system 700, including the input and output of data to and from software applications (not shown). The operating system provides an interface between the software applications being executed on the system and the hardware components of the system. Any suitable operating system may be used, such as the LINUX Operating System, the Apple Macintosh Operating System, available from Apple Computer Inc. of Cupertino, Calif., UNIX operating systems, Microsoft® Windows® operating systems, BSD operating systems, and the like. Other implementations are possible.

The elements of the computer system 700 are described in greater detail below. In particular, the network interface 716 provides communication between the computer system 700 and any of a wide range of networks, such as an Ethernet (e.g., IEEE 802.3) network, a backplane, etc. The mass storage 718 provides permanent storage for the data and programming instructions to perform the above-described processes and features implemented by the respective computing systems identified above, whereas the system memory 714 (e.g., DRAM) provides temporary storage for the data and programming instructions when executed by the processor 702. The I/O ports 720 may be one or more serial and/or parallel communication ports that provide communication between additional peripheral devices, which may be coupled to the computer system 700.

The computer system 700 may include a variety of system architectures, and various components of the computer system 700 may be rearranged. For example, the cache 704 may be on-chip with processor 702. Alternatively, the cache 704 and the processor 702 may be packed together as a “processor module”, with processor 702 being referred to as the “processor core”. Furthermore, certain embodiments of the invention may neither require nor include all of the above components. For example, peripheral devices coupled to the standard I/O bus 708 may couple to the high performance I/O bus 706. In addition, in some embodiments, only a single bus may exist, with the components of the computer system 700 being coupled to the single bus. Moreover, the computer system 700 may include additional components, such as additional processors, storage devices, or memories.

In general, the processes and features described herein may be implemented as part of an operating system or a specific application, component, program, object, module, or series of instructions referred to as “programs”. For example, one or more programs may be used to execute specific processes described herein. The programs typically comprise one or more instructions in various memory and storage devices in the computer system 700 that, when read and executed by one or more processors, cause the computer system 700 to perform operations to execute the processes and features described herein. The processes and features described herein may be implemented in software, firmware, hardware (e.g., an application specific integrated circuit), or any combination thereof.

In one implementation, the processes and features described herein are implemented as a series of executable modules run by the computer system 700, individually or collectively in a distributed computing environment. The foregoing modules may be realized by hardware, executable modules stored on a computer-readable medium (or machine-readable medium), or a combination of both. For example, the modules may comprise a plurality or series of instructions to be executed by a processor in a hardware system, such as the processor 702. Initially, the series of instructions may be stored on a storage device, such as the mass storage 718. However, the series of instructions can be stored on any suitable computer readable storage medium. Furthermore, the series of instructions need not be stored locally, and could be received from a remote storage device, such as a server on a network, via the network interface 716. The instructions are copied from the storage device, such as the mass storage 718, into the system memory 714 and then accessed and executed by the processor 702. In various implementations, a module or modules can be executed by a processor or multiple processors in one or multiple locations, such as multiple servers in a parallel processing environment.

Examples of computer-readable media include, but are not limited to, recordable type media such as volatile and non-volatile memory devices; solid state memories; floppy and other removable disks; hard disk drives; magnetic media; optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs)); other similar non-transitory (or transitory), tangible (or non-tangible) storage medium; or any type of medium suitable for storing, encoding, or carrying a series of instructions for execution by the computer system 700 to perform any one or more of the processes and features described herein.

For purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the description. It will be apparent, however, to one skilled in the art that embodiments of the disclosure can be practiced without these specific details. In some instances, modules, structures, processes, features, and devices are shown in block diagram form in order to avoid obscuring the description. In other instances, functional block diagrams and flow diagrams are shown to represent data and logic flows. The components of block diagrams and flow diagrams (e.g., modules, blocks, structures, devices, features, etc.) may be variously combined, separated, removed, reordered, and replaced in a manner other than as expressly described and depicted herein.

Reference in this specification to “one embodiment”, “an embodiment”, “other embodiments”, “one series of embodiments”, “some embodiments”, “various embodiments”, or the like means that a particular feature, design, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of, for example, the phrase “in one embodiment” or “in an embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, whether or not there is express reference to an “embodiment” or the like, various features are described, which may be variously combined and included in some embodiments, but also variously omitted in other embodiments. Similarly, various features are described that may be preferences or requirements for some embodiments, but not other embodiments. Furthermore, reference in this specification to “based on” can mean “based, at least in part, on”, “based on at least a portion/part of”, “at least a portion/part of which is based on”, and/or any combination thereof.

The language used herein has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims. 

What is claimed is:
 1. A computer-implemented method comprising: acquiring, by a computing system, shape data representative of one or more polygons; producing, by the computing system, at least one serialization format based on the shape data; packaging, by the computing system, the at least one serialization format into a proprietary package that is representative of the one or more polygons; utilizing, by the computing system, at least a portion of the proprietary package for one or more applications.
 2. The computer-implemented method of claim 1, further comprising: analyzing the shape data representative of the one or more polygons; identifying, based on analyzing the shape data, at least one error associated with the shape data; and correcting, prior to producing the at least one serialization format, the at least one error.
 3. The computer-implemented method of claim 1, wherein the shape data representative of the one or more polygons is associated with at least one of an Environmental Systems Research Institute (ESRI) format, a Network Common Data Form (NetCDF) format, a drawing (DWG) format, a Computer-Aided Design (CAD) format, a Well-Known Text (WKT) format, or a GeoJSON format.
 4. The computer-implemented method of claim 1, wherein the at least one serialization format is associated with at least one of an R serialization format, a data warehouse-compatible format, or a fortified format.
 5. The computer-implemented method of claim 1, wherein the proprietary package enables shape data acquired from different data sources to be standardized.
 6. The computer-implemented method of claim 1, wherein the one or more applications are associated with at least one of an entity framework, a geo-based application programming interface (API), or a real-time process.
 7. The computer-implemented method of claim 6, wherein the one or more applications are associated with the entity framework, and wherein the one or more applications cause at least the portion of the proprietary package to be imported into a distributed data store that provides access to a social graph associated with a social networking system.
 8. The computer-implemented method of claim 6, wherein the one or more applications are associated with the real-time process, and wherein the one or more applications cause at least the portion of the proprietary package to be utilized for real-time querying.
 9. The computer-implemented method of claim 6, wherein the one or more applications are associated with the geo-based application programming interface (API), and wherein the one or more applications cause at least the portion of the proprietary package to be utilized for at least one of: 1) mapping a set of tiles associated with a social networking system to a set of polygons or 2) providing a prediction of a location for a user of the social networking system.
 10. The computer-implemented method of claim 9, wherein mapping the set of tiles associated with the social networking system to the set of polygons includes: 1) mapping a first subset of tiles to a first subset of polygons and 2) mapping a second subset of tiles to a second subset of polygons, wherein mapping the first subset of tiles to the first subset of polygons is performed via a first computing system, and wherein mapping the second subset of tiles to the second subset of polygons is performed via a second computing system.
 11. A system comprising: at least one processor; and a memory storing instructions that, when executed by the at least one processor, cause the system to perform: acquiring shape data representative of one or more polygons; producing at least one serialization format based on the shape data; packaging the at least one serialization format into a proprietary package that is representative of the one or more polygons; utilizing at least a portion of the proprietary package for one or more applications.
 12. The system of claim 11, wherein the instructions cause the system to further perform: analyzing the shape data representative of the one or more polygons; identifying, based on analyzing the shape data, at least one error associated with the shape data; and correcting, prior to producing the at least one serialization format, the at least one error.
 13. The system of claim 11, wherein the shape data representative of the one or more polygons is associated with at least one of an Environmental Systems Research Institute (ESRI) format, a Network Common Data Form (NetCDF) format, a drawing (DWG) format, a Computer-Aided Design (CAD) format, a Well-Known Text (WKT) format, or a GeoJSON format.
 14. The system of claim 11, wherein the at least one serialization format is associated with at least one of an R serialization format, a data warehouse-compatible format, or a fortified format.
 15. The system of claim 11, wherein the one or more applications are associated with at least one of an entity framework, a geo-based application programming interface (API), or a real-time process.
 16. A non-transitory computer-readable storage medium including instructions that, when executed by at least one processor of a computing system, cause the computing system to perform a method comprising: acquiring shape data representative of one or more polygons; producing at least one serialization format based on the shape data; packaging the at least one serialization format into a proprietary package that is representative of the one or more polygons; utilizing at least a portion of the proprietary package for one or more applications.
 17. The non-transitory computer-readable storage medium of claim 16, wherein the instructions cause the computing system to further perform: analyzing the shape data representative of the one or more polygons; identifying, based on analyzing the shape data, at least one error associated with the shape data; and correcting, prior to producing the at least one serialization format, the at least one error.
 18. The non-transitory computer-readable storage medium of claim 16, wherein the shape data representative of the one or more polygons is associated with at least one of an Environmental Systems Research Institute (ESRI) format, a Network Common Data Form (NetCDF) format, a drawing (DWG) format, a Computer-Aided Design (CAD) format, a Well-Known Text (WKT) format, or a GeoJSON format.
 19. The non-transitory computer-readable storage medium of claim 16, wherein the at least one serialization format is associated with at least one of an R serialization format, a data warehouse-compatible format, or a fortified format.
 20. The non-transitory computer-readable storage medium of claim 16, wherein the one or more applications are associated with at least one of an entity framework, a geo-based application programming interface (API), or a real-time process. 